home *** CD-ROM | disk | FTP | other *** search
- Path: news1.ucsd.edu!usenet
- From: djohnson@tartarus.ucsd.edu (Darin Johnson)
- Newsgroups: comp.edu,comp.lang.c,comp.lang.c++
- Subject: Re: C or C++ for a 14-year old?
- Date: 15 Jan 1996 17:13:32 -0800
- Organization: UCSD Computer Science and Engineering Department
- Sender: djohnson@tartarus.ucsd.edu
- Message-ID: <qqd98lgcw3.fsf@tartarus.ucsd.edu>
- References: <4b30ld$lp2$1@mhafc.production.compuserve.com>
- <4d4jeh$fv1@wombat.melbpc.org.au>
- <w+PJjMD4ED1aLz3@dexam.another.gun.de> <4ddsg4$p4e@sundog.tiac.net>
- NNTP-Posting-Host: tartarus.ucsd.edu
- In-reply-to: amoreira@nine.com's message of Mon, 15 Jan 1996 15:42:33 GMT
- X-Newsreader: Gnus v5.0
-
- amoreira@nine.com (Alberto C Moreira) writes:
- > Still, there's no worse restriction on a programmer than not to be
- > able to talk directly to the hardware.
-
- And most systems allow this, with guidelines. Ie, you have to lock
- the hardware before using it, or restrict access to superuser or
- kernel programs, etc. Sure, that can be complex, cumbersome, and
- impossible for many users; but it's *necessary* in any system that has
- multiple users or multiple processes. The fact that there's nothing
- to do in DOs to get direct hardware acess derives from it's origin as
- a one-user one-application-at-a-time system; the fact that UNIX makes
- it hard is from it's background as a multiuser multiprocess system.
- Then again, in UNIX you rarely have to worry about what sort of sound
- card or video card you have like you have to in DOS.
- --
- Darin Johnson
- djohnson@ucsd.edu
- The trouble with conspiracy theories are that they assume
- the government is organized.
-